Add record codec for key-value maps#6
Merged
Merged
Conversation
kasperisager
approved these changes
Jul 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a
record(key_codec, value_codec)primitive: a uint entry-count prefix followed by each key then value encoded in insertion order, byte-for-byte compatible with JScompact-encoding'sexports.record. Iteratesdict.items()(insertion order, matching JSObject.keysfor ordinary string keys); decode rebuilds a fresh dict in wire order. No size guard (JSrecordhas none, unlikearray).Runtime layer for encoding top-level record types; a later hyperschema-python change will emit
c.record(...)for them.Additive: no existing codec is touched. Re-exported from
__init__.py. 245 tests pass (record byte-exact + order + roundtrip), ruff clean.